Skip to content

Bump mypy from 2.2.0 to 2.3.0 - #142

Merged
docktermj merged 1 commit into
mainfrom
dependabot/pip/mypy-2.3.0
Aug 6, 2026
Merged

Bump mypy from 2.2.0 to 2.3.0#142
docktermj merged 1 commit into
mainfrom
dependabot/pip/mypy-2.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps mypy from 2.2.0 to 2.3.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Packaging changes

Mypy 2.3

We've just uploaded mypy 2.3.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

The Upcoming Switch to the New Native Parser

We are planning to enable the new native parser (--native-parser) by default soon. We recommend that you test the native parser in your projects and report any issues in the mypy issue tracker.

Mypyc Free-threading Memory Safety

Free-threaded Python builds that don't have the GIL require additional synchronization primitives or lock-free algorithms to ensure memory safety when there are race conditions (for example, when a thread reads a list item while another thread writes the same list item concurrently). This release greatly improves memory safety of free threading.

List operations are now memory-safe on free threaded Python builds, even in the presence of race conditions. This has some performance cost. For list-heavy workloads, using librt.vecs.vec instead of list is often significantly faster, but note that vec is not (and likely won't be) fully memory safe, and the user is expected to avoid race conditions. The newly introduced librt.threading.Lock helps with this. Using variable-length tuples can also be more efficient than lists, since tuples are immutable and don't require expensive synchronization to ensure memory safety.

Instance attribute access is also (mostly) memory safe now on free-threaded builds in the presence of race conditions. We are planning to fix the remaining unsafe cases in a future release.

Full list of changes:

  • Make attribute access memory safe on free-threaded builds (Jukka Lehtosalo, PR 21705)
  • Fix unsafe borrowing of instance attributes with free-threading (Jukka Lehtosalo, PR 21688)
  • Make list get/set item more memory safe on free-threaded builds (Jukka Lehtosalo, PR 21683)
  • Don't borrow list items on free-threaded builds (Jukka Lehtosalo, PR 21679)
  • Make multiple assignment from list memory-safe on free-threaded builds (Jukka Lehtosalo, PR 21684)

... (truncated)

Commits
  • 8aabf84 Drop +dev from version
  • 4d8ad2a Update changelog for 2.3 release (#21728)
  • 2c21546 [mypyc] Update documentation of race conditions under free threading (#21726)
  • a9f62a3 [mypyc] Make attribute access memory safe on free-threaded builds (#21705)
  • 0faa413 Use PYODIDE environment variable for Emscripten cross-compilation detection...
  • 3d75cdb [mypyc] Borrow final attributes more aggressively (#21702)
  • 24c237d [mypyc] Improve documentation of Final (#21713)
  • b5be217 [mypyc] Update free threading Python compatibility docs (#21711)
  • cbcb51a Narrow for frozendict membership check (#21709)
  • af2bc0f Sync typeshed (#21707)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 4, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner August 4, 2026 01:32
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 4, 2026
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

🤖 Claude Code Review

Code Review: Bump mypy from 2.2.0 to 2.3.0

This is an automated Dependabot dependency bump touching a single line in pyproject.toml (line 77), consistent with prior merged bumps in this repo (e.g. #139, #140, #141). No source code changes are included.

Code Quality

  • ✅ Style conventions: pyproject.toml:77 — version pin format matches surrounding lines ("mypy==2.3.0").
  • ✅ No commented-out code: N/A, no such content in diff.
  • ✅ Meaningful variable names: N/A, no code changed.
  • ✅ DRY principle: N/A.
  • ✅ Defects: No logic changes; this only affects the lint dependency group used for dev tooling, not runtime behavior. No functional risk to src/csv_analyzer.py, src/csv_mapper.py, or src/csv_functions.py.
  • ✅ CLAUDE.md review: .claude/CLAUDE.md unchanged by this PR; not applicable here.

Testing

  • ✅ N/A — dependency version bump only, no new functions/endpoints introduced.
  • ⚠️ Not verified in this review: whether mypy==2.3.0 introduces new/stricter type-checking rules that could cause the pylint/mypy lint step to fail against existing code (e.g. src/*.py). No network access is available in this run to check the mypy 2.3.0 changelog, so I could not confirm this. Recommend confirming CI (lint job) passes green on this PR before merge.

Documentation

Security

  • ✅ No hardcoded credentials: Confirmed, diff only contains a version string.
  • ✅ Input validation: N/A.
  • ✅ Error handling: N/A.
  • ✅ No sensitive data in logs: N/A.
  • ✅ License files (.lic) / AQAAAD strings: Confirmed no .lic files or AQAAAD-prefixed strings present in this diff.

Summary

No blocking issues. This is a routine, low-risk dev-dependency version bump. Only recommendation is to confirm the lint/mypy CI check passes with the new version before merging, since 2.3.0 could surface new type errors in existing code that weren't caught under 2.2.0.

Automated code review analyzing defects and coding standards

@dependabot
Bump mypy from 2.2.0 to 2.3.0
11680f8 
Bumps [mypy](https://github.com/python/mypy) from 2.2.0 to 2.3.0.
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v2.2.0...v2.3.0)

---
updated-dependencies:
- dependency-name: mypy
  dependency-version: 2.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/mypy-2.3.0 branch from a254968 to 11680f8 Compare August 6, 2026 01:35
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown

🤖 Claude Code Review

PR Code Review

Diff summary: Single-line dependency bump — mypy==2.2.0 → mypy==2.3.0 in pyproject.toml (lint dependency group). This is an automated Dependabot-style bump.

Code Quality

  • ✅ Style conventions — trivial version string change, follows existing formatting of the lint array.
  • ✅ No commented-out code.
  • ✅ Meaningful variable names — N/A, no variables introduced.
  • ✅ DRY principle — N/A.
  • ✅ Defects/bugs/logic errors — N/A, no logic changed. One note: this bump could introduce new mypy errors on the existing codebase since mypy 2.3.0 may enable new checks or tighten inference vs 2.2.0. I could not run mypy in this environment to confirm the bump is clean — recommend confirming CI's lint job passes on this PR before merging.
  • ✅ CLAUDE.md consideration — no changes to .claude/CLAUDE.md in this diff; existing project instructions remain generic and environment-agnostic, no issue found.

Testing

  • N/A — dependency version bump, no new functions/endpoints. Test coverage expectation doesn't apply.

Documentation

  • ✅ No README/API doc changes needed for a lint tool bump.
  • ⚠️ CHANGELOG.md not updated — if this repo tracks dependency bumps in CHANGELOG.md (worth checking repo convention; many Dependabot PRs in this repo appear to skip changelog entries based on commit history, e.g. 8387029 Bump coverage..., 9a6e22d Bump virtualenv... — so this is likely consistent with existing practice, not a gap).
  • ✅ Markdown/CommonMark — no markdown files touched.

Security

  • ✅ No hardcoded credentials.
  • ✅ No input validation concerns — build config only.
  • ✅ No error handling concerns.
  • ✅ No sensitive data in logs.
  • ✅ No .lic files or AQAAAD-prefixed strings present in this diff.

Overall

No blocking issues. This is a low-risk, mechanical dependency version bump consistent with other recent Dependabot commits in this repo's history (mypy, coverage, virtualenv bumps). Recommend merging once CI (lint job) passes with the new mypy version.

Automated code review analyzing defects and coding standards

@docktermj
docktermj merged commit 846645b into main Aug 6, 2026
12 checks passed
@docktermj
docktermj deleted the dependabot/pip/mypy-2.3.0 branch August 6, 2026 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@docktermj docktermj docktermj approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@docktermj @senzingdevops